HTTP setup

The DINGO-Stack runs two webservers on the DINGO device that enables BACnet functionalities and configuration of the DINGO device over HTTP and HTTPS.

Use HTTP: Determines if the HTTP server should be used.

HTTP port: Determines the HTTP port. 80 is the default port for HTTP.

Use HTTPS: Determines if the HTTPS server should be used.

HTTPS port: Determines the HTTPS port. 443 is the default port for HTTPS.

Note: Both HTTP and HTTPS servers can be used at the same time.
Important: If neither the HTTP nor HTTPS servers are used then the DINGO-Manager cannot communicate with the device.

The reload icon in the upper right corner can be clicked to reload the information from the DINGO device.

Certificate management is used when the HTTPS server is running. A certificate is created for a specific IP every time the DINGO device boots. The IP used is the IP of the primary interface used to connect to the Internet (Ethernet, wireless or modem).

The certificate is signed by a root CA certificate that must be downloaded and installed into the users browsers trusted certificate repositories. Otherwise the browser will complain saying that it does not trust the DINGO device when browsing over HTTPS.

There is a hyperlink on the dialog shown in the screenshot above that downloads the certificate from the DINGO device. The root CA certificate is common for all DINGO devices and needs to be downloaded and installed only once.

Extension: When the DINGO device boots, its IP and hostname are added to the so called SAN (Subject alternative name). This is important so that the browser trusts the IP and hostname. An example of the content looks like this:

If the DINGO device is behind a router that has an public IP and has a port forwarded to the DINGO device, then the user needs to add the IP of the router to the SAN, so that the browser also trusts the router IP. If the IP is 80.90.100.200 then the contents now looks like this: